The DBMS must maintain the binding of security labels to information with sufficient assurance that the information/attribute association can be used as the basis for automated policy actions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-32166	SRG-APP-000008-DB-000185	SV-42483r1_rule		Medium

Description
Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These attributes are typically associated with internal data structures (e.g., records, buffers, files) within the application and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. Organizations define the security attributes of their data (e.g., classified, FOUO). Applications generating and/or processing data assigned these organization defined security attributes must maintain the binding of these attributes to the data when the data is transmitted. If the application does not maintain the data security attributes when it transmits the data, there is a risk of data compromise. The sensitivity marking or labeling of data items promotes the correct handling and protection of data. Without such notification, the user may unwittingly disclose sensitive data to unauthorized users. Security labels must be correctly maintained throughout transmission.

Description

Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These attributes are typically associated with internal data structures (e.g., records, buffers, files) within the application and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. Organizations define the security attributes of their data (e.g., classified, FOUO). Applications generating and/or processing data assigned these organization defined security attributes must maintain the binding of these attributes to the data when the data is transmitted. If the application does not maintain the data security attributes when it transmits the data, there is a risk of data compromise. The sensitivity marking or labeling of data items promotes the correct handling and protection of data. Without such notification, the user may unwittingly disclose sensitive data to unauthorized users. Security labels must be correctly maintained throughout transmission.

STIG	Date
Database Security Requirements Guide	2012-07-02

Details

Check Text ( C-40679r3_chk )
Review system documentation to determine if the labeling of sensitive data is required under organization defined guidelines. If the labeling of sensitive data is not required, this is NA. Review security labels after transmission via database connections, links, files, xml, and any other transmission method, to verify labels are intact and correct. If labels are not intact and correct after data transmission, this is a finding.

Check Text ( C-40679r3_chk )

Review system documentation to determine if the labeling of sensitive data is required under organization defined guidelines. If the labeling of sensitive data is not required, this is NA.

Review security labels after transmission via database connections, links, files, xml, and any other transmission method, to verify labels are intact and correct. If labels are not intact and correct after data transmission, this is a finding.

Fix Text (F-36090r1_fix)
Configure the DBMS and other database application code to properly manage security labels during transmission.